test_json.py reports some failures unrelated to this PR:

 test_json.py::test_schema_valid[/home/runner/work/ocds_location_extension/ocds_location_extension/release-schema.json-release-schema.json-data0]
  release-schema.json has "properties" within "properties" at /definitions/Location/properties/geometry

test_json.py::test_schema_valid[/home/runner/work/ocds_location_extension/ocds_location_extension/release-schema.json-release-schema.json-data0]
  release-schema.json has "properties" within "properties" at /definitions/Location/properties/gazetteer

and some failures relating to missing ids:

 test_json.py::test_json_merge_patch
  release-schema.json is missing "id" in "items/properties" at /definitions/

However, based on the logic in https://ocds-standard-development-handbook.readthedocs.io/en/latest/meta/schema_style_guide.html#id-field I'm not sure that an id field is required for addresses or locations, although we did add an id field to Location in OC4IDS.

@jpmckinney please can you add @odscrachel and @mrshll1001 to the team for the open-contracting-extensions organisation so that I can request a review from them?

They have now been invited. I'll look into the tests and add exceptions as needed.

Thanks!

@duncandewhurst Please set "wholeListMerge": true for those arrays, to make the merge behavior explicit. Feel free to add this clarification to the handbook as well.

@jpmckinney I think this is ready to be merged?

Yes, somehow fell out of my inbox.